Skip to content

fix: only block release on fixed issues with higher severity than low #179

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Mar 20, 2025

Conversation

obs-gh-mattcotter
Copy link
Collaborator

@obs-gh-mattcotter obs-gh-mattcotter commented Mar 20, 2025

Description

Only block release on fixed issues with higher severity than low. This will ensure we can still release in the 180 day window we have to fix low severity issues, or when we know about an issue that has no fix.

@obs-gh-mattcotter obs-gh-mattcotter force-pushed the mc/vuln-check branch 2 times, most recently from ec68dad to b40a603 Compare March 20, 2025 17:13
@obs-gh-mattcotter obs-gh-mattcotter changed the title fix: only block release on critical or high severity issues fix: only block release on fixed issues with higher severity than low Mar 20, 2025
@@ -7,11 +7,6 @@ on:
description: "The branch on which to run the vulnerability check"
required: true
default: "main"
workflow_call:
Copy link
Collaborator

@obs-gh-alexlew obs-gh-alexlew Mar 20, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

why are we removing this from the full check? I'd still maybe want to run this against an arbitrary branch

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Manual runs go through the workflow_dispatch (https://docs.github.com/en/actions/writing-workflows/choosing-when-your-workflow-runs/events-that-trigger-workflows#workflow_dispatch), which still has the branch input above.

If we think we would call this full run workflow as a step in a different workflow, then I can leave in the workflow_call. I didn't foresee that happening though

@obs-gh-mattcotter obs-gh-mattcotter merged commit 1c232ed into main Mar 20, 2025
8 checks passed
@obs-gh-mattcotter obs-gh-mattcotter deleted the mc/vuln-check branch March 20, 2025 20:28
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants